5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
- Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 1-4: Understanding Process Design

Preparing for Runtime


When you choose to run a process after initially defining or modifying it, APPX needs to prepare it for operation. During this preparation step, called compilation, the system translates the source specifications into detailed instructions that optimize runtime performance. This translated format of a process is called an executable module, abbreviated as EM. Because each process has its own EM, usually only a small portion of an application needs recompilation at runtime. APPX is designed so that you can immediately invoke a new or modified process without having to execute a separate step to compile it. Whenever you choose to run a process, APPX automatically determines whether compilation is required by checking all referenced components in the application, including the data dictionary, to see if any changes have been made since the last compilation. If changes are detected, the system recompiles the process and creates a new executable module; if not, the system uses the current executable module.

The system also processes the data dictionary specifications into an executable format. The dictionary operates differently from processes, and requires a separate processing step. If you make any changes to the data dictionary specifications, APPX will process them before executing any process that references modified dictionary components. A separate step is provided to allow you to process the dictionary and to coordinate other related design activities, such as file restructuring.

Application Design Manual                                         "Powered by Appx Software"

76

©2006 By APPX Software, Inc. All Rights Reserved